home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group94b.txt
/
000013_icon-group-sender _Tue Aug 23 22:46:00 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1995-02-09
|
2KB
Received: by cheltenham.cs.arizona.edu; Tue, 23 Aug 1994 16:43:22 MST
Date: 23 Aug 94 22:46 GMT
From: NOR0048@applelink.apple.com (HoyskoleData,Oslo,NO,IER)
Subject: ProIcon 2.0 and LF chars
To: ICON-GROUP@cs.arizona.edu
Message-Id: <777682525.3038677@AppleLink.Apple.COM>
Errors-To: icon-group-errors@cs.arizona.edu
Re: ProIcon 2.0 and Line Feed characters
I've just started doing some simple programming projects in ProIcon 2.0 on
my Macintosh LC (w/7.1) and IIci (w/7.0). Different kinds of text file
conversion was what I planned to use ProIcon for in the beginning. Now I've
just got my first BIG surprise:
An expression like writes(outFile,"\x0A") turns out to write a Carriage Return
character instead of a Line Feed! Using "^J" instead of "\x0A" makes no
difference. As far as I can see, the translation of hex 0A into 0D takes place
during run-time. That \n should produce a CR on a Mac is quite natural, but
not at all being able to write LF's to a text file is hard to accept,
especially if you deal with cross-platform text conversion.
Does anybody know how to solve this? Is it possible to patch the run-time code
without loosing the CR's you normally expect from \n and "write"?
If you have an answer or comment, I would be very pleased if you could email
it to this address: Nor0048@applelink.apple.com, since I have no personal
Internet address at the moment. (I expect to get one in a couple of weeks.)
Sincerely,
Jon Kleiser
Oslo, Norway